iter conservation efforts: save the endangered .iter() and .into_iter() #3119
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Every day, more iters are lost, discarded as unwanted, to such hazards
as "concision" and "brevity". Won't someone think of the poor .iter()
and .into_iter(), that future generations may continue to admire them
and their self-documenting properties in their many and varied natural
habitats, and not merely in a zoo of (en)closures?
Make explicit_iter_loop and explicit_into_iter_loop allow-by-default, so
that people can turn them on if they want to enforce that style; avoid
presenting them as the idiomatic Rust style, rather than just a style.